Config file changes in Sitecore CMS and DMS 7.2 rev. 151021 compared to CMS and DMS 7.2 rev. 150408
This Service Pack requires you to make changes to the following files:
- /App_Config/FieldTypes.config
- /App_Config/Commands.config
- /App_Config/Include/Sitecore.ContentSearch.config
- /App_Config/Include/Sitecore.Buckets.config
Depending on search provider, you should also update the appropriate files below:
Sitecore solution configured to use Lucene:
- /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Web.config
- /App_Config/Include/Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config
Sitecore solution configured to use Solr:
- /App_Config/Include/Sitecore.ContentSearch.Solr.Indexes.config
Depending on the database, you should also update the appropriate files:
Sitecore solution configured to use MS SQL Server:
Sitecore solution configured to use Oracle:
Added configuration files:
- /App_Config/Include/Sitecore.DefaultLanugage.config
You can download the clean configuration files for Sitecore CMS and DMS 7.2 rev. 151021:
Changes in FieldTypes.config
The following change has been made to the /App_Config/FieldTypes.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /App_Config/FieldTypes.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- Add the following node (you can add it at any place in the <configuration> section)
<fieldType name="Name Lookup Value List" type="Sitecore.Data.Fields.NameValueListField,Sitecore.Kernel" />
Changes in Commands.config
The following change has been made to the /App_Config/Commands.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /App_Config/Commands.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- Add the following node (you can add it at any place in the <configuration> section)
<command name="webedit:editnumber" type="Sitecore.Shell.Applications.WebEdit.Commands.EditNumber,Sitecore.Client"/>
<command name="webedit:editinteger" type="Sitecore.Shell.Applications.WebEdit.Commands.EditInteger,Sitecore.Client"/>
Changes in Sitecore.ContentSearch.config
The following changes have been made to the /App_Config/Include/Sitecore.ContentSearch.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /App_Config/Include/Sitecore.ContentSearch.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- Change the node <event name="indexing:start" /> to:
<event name="indexing:start">
<handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="IndexingStartedHandler" />
</event>
- In the <event name="indexing:end"> node, add:
<handler type="Sitecore.ContentSearch.Events.IndexingEventHandler, Sitecore.ContentSearch" method="IndexingEndedHandler" />
- In the <settings> section (you can add it at any place in the <settings> section), add:
<!-- INDEX UPDATE BATCH SIZE
Determines the amount of items that should be processed during the index update within a batch.
Default value: 300
-->
<setting name="ContentSearch.IndexUpdate.BatchSize" value="300" />
Changes in Sitecore.Buckets.config
The following changes have been made to the /App_Config/Include/Sitecore.Buckets.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) as compared to the /App_Config/Include/Sitecore.Buckets.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- In the <pipelines> section, between the <publish> and the <renderField> pipelines, add:
<publishItem>
<processor patch:after="processor[@type='Sitecore.Publishing.Pipelines.PublishItem.DetermineAction, Sitecore.Kernel']" type="Sitecore.Buckets.Pipelines.PublishItem.ProcessActionForBucketStructure, Sitecore.Buckets" />
</publishItem>
Changes in Sitecore.ContentSearch.Lucene.Index.Web.config
The following changes have been made to the /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Web.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /App_Config/Include/Sitecore.ContentSearch.Lucene.Index.Web.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- In the <policies hint="list:AddCommitPolicy"> node, change:
<policy type="Sitecore.ContentSearch.TimeIntervalCommitPolicy, Sitecore.ContentSearch" />
To:
<policy type="Sitecore.ContentSearch.ModificationCountCommitPolicy, Sitecore.ContentSearch">
<Limit>300</Limit>
</policy>
Changes in Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config (Sitecore.ContentSearch.Solr.Indexes.config)
The following changes have been made to the /App_Config/Include/Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /App_Config/Include/Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- Before the <rebuildAfterFullPublish …> node, add:
<!-- REINDEX ON PUBLISH END SINGLE INSTANCE
This strategy is triggered on publish:end and uses the EventQueue to incrementally rebuild the index. The strategy contains all indexes which belong to it. -->
<onPublishEndAsyncSingleInstance type="Sitecore.ContentSearch.Maintenance.Strategies.OnPublishEndAsynchronousSingleInstanceStrategy, Sitecore.ContentSearch" singleInstance="true">
<param desc="database">web</param>
<!-- Whether or not a full index rebuild should be triggered when the number of items in the EventQueue exceeds the number specified in ContentSearch.FullRebuildItemCountThreshold. -->
<CheckForThreshold>true</CheckForThreshold>
</onPublishEndAsyncSingleInstance>
- In the start of the <fieldReaders> node, add:
<param desc="id">defaultFieldReaderMap</param>
Changes in Web.config (Web.config.Oracle)
The following changes have been made to the /Web.config file of Sitecore CMS 7.2 rev. 151021 (Service Pack-2) compared to the /Web.config file of Sitecore CMS 7.2 rev. 150408 (Update-4).
- In the <getMediaStream> pipeline in <pipelines> section, add:
As the first processor:
<processor type="Sitecore.Resources.Media.SaveColorProfileProcessor, Sitecore.Kernel" />
As the last processor:
<processor type="Sitecore.Resources.Media.RestoreColorProfileProcessor, Sitecore.Kernel" />
- In the <renderField> pipeline, after the GetDocxFieldValue processor, add:
<processor type="Sitecore.Pipelines.RenderField.GetIntegerFieldValue, Sitecore.Kernel" />
<processor type="Sitecore.Pipelines.RenderField.GetNumberFieldValue, Sitecore.Kernel" />
- In the <encodeNameReplacements> section, add:
<replace mode="on" find=" " replaceWith="-" />
- In the <mediaTypes> section, remove:
<mediaType name="SVG image" extensions="svg">
<mimeType>image/svg+xml</mimeType>
<forceDownload>false</forceDownload>
<sharedTemplate>system/media/unversioned/image</sharedTemplate>
<versionedTemplate>system/media/versioned/image</versionedTemplate>
<mediaValidator type="Sitecore.Resources.Media.ImageValidator" />
<thumbnails>
<generator type="Sitecore.Resources.Media.ImageThumbnailGenerator, Sitecore.Kernel">
<extension>png</extension>
</generator>
<width>150</width>
<height>150</height>
<backgroundColor>#FFFFFF</backgroundColor>
</thumbnails>
</mediaType>
- In the <settings> section, after the <setting name="ItemCloning.NonInheritedFields" value="" /> node, add:
<!-- ITEM CLONING - INHERIT WORKFLOW DATA
Specify whether you want the workflow and workflow state fields to be inherited by clones from their source item.
Note: When you change the setting value, clones move in or out the workflow, which may affect their behavior, for example, on publishing.
Default value: false
-->
<setting name="ItemCloning.InheritWorkflowData" value="false" />
<!-- ITEM CLONING - FORCE UPDATE
Specify whether clones should be updated automatically when:
- a new version is added to the original item.
- a new language is added to the original item.
- a new sub-item is added to the original item.
Note: If true, all the clones of the original item are updated automatically.
Default value: false
-->
<setting name="ItemCloning.ForceUpdate" value="false" />
- In <settings> section, after the <setting name="LicenseFile" value="$(dataFolder)/license.xml" /> node, add:
<!-- LINK DATABASE - MAXIMUM BATCH SIZE
This setting specifies the maximum number of records that Compact method can process in a single iteration.
If you set this value too low, it can cause excessive amounts of network traffic and may have a significant impact
on system throughput.
If you set this value too high, it may affect tasks that require communication with SQL Server. For example, it may affect the size of transactions
sent to SQL Server and this might require you to set higher 'lock timeout' values as it takes longer to process large batches.
Default: 1000
-->
<setting name="LinkDatabase.MaximumBatchSize" value="1000" />
- In the <settings> section, after the <setting name="Media.FileFolder" value="/App_Data/MediaFiles" /> node, add:
<!-- MEDIA - FILE SYSTEM WATCHER - BUFFER SIZE
The size (in bytes) of the internal buffer used by the file system watchers that monitor the file system change
notifications and raise events when a directory, or file in a directory, changes.
If you get log entries about internal buffer overflow, increasing the value of this setting may solve this problem.
The minimum size is 4096 (4 KB).
The maximum size is 65536 (64 KB).
Be aware that increasing this value could hurt performance. See http://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher.internalbuffersize%28v=vs.110%29.html.
Default value: 8192
-->
<setting name="Media.FileSystemWatcher.BufferSize" value="8192" />
- In the <settings> section, after the <setting name="Media.WhitespaceReplacement" value=" " /> node, add:
<!-- REMOVE UNUSED BLOBS ON SAVE
Specifies whether unused blobs should be deleted from an item when it is saved. This setting only checks items that contain blob fields.
To improve performance during a bulk upload of media files, set this setting to "false".
When this setting is set to "false", you must run the CleanupDatabase task periodically.
Default value: true.
-->
<setting name="RemoveUnusedBlobsOnSave" value="true" />
- In the <settings> section, after the <setting name="MediaResponse.SlidingExpiration" value="" /> node, add:
<!-- MEDIA RESPONSE - VARY HEADER
Specifies the value for the Vary HTTP header to use in media response headers.
Set it to "" to omit this header.
Default value: ""
-->
<setting name="MediaResponse.VaryHeader" value="" />
- In the <settings> section, after the <setting name="ViewStateStore" value="Sitecore.Web.UI.Sheer.FileViewStateStore,Sitecore.Kernel" /> node, add:
<!-- WEB EDIT JQuery UI STYLESHEET
The stylesheet to include in the page editor in WebEdit mode.
Default value: /sitecore/shell/Controls/Lib/jQuery/jQueryUI/1.10.3/smoothness/jquery-ui-1.10.3.min.css
-->
<setting name="WebEdit.JQueryUIStylesheet" value="/sitecore/shell/Controls/Lib/jQuery/jQueryUI/1.10.3/smoothness/jquery-ui-1.10.3.min.css" />
- In the <system.webServer> section, after the <add type="Sitecore.Web.HttpModule,Sitecore.Kernel" name="SitecoreHttpModuleExtensions" /> node, add:
<add type="Sitecore.Web.HttpModuleDisabler, Sitecore.Kernel" name="SitecoreHttpModuleDisabler" />